home *** CD-ROM | disk | FTP | other *** search
- Path: informatik.tu-muenchen.de!fischerj
- From: fischerj@informatik.tu-muenchen.de (Juergen "Rally" Fischer)
- Newsgroups: comp.sys.amiga.programmer
- Subject: QBlit & BlitBitMapRastport = lock
- Date: 25 Jan 1996 15:22:23 GMT
- Organization: Technische Universitaet Muenchen, Germany
- Distribution: world
- Message-ID: <4e877f$jtf@sunsystem5.informatik.tu-muenchen.de>
- NNTP-Posting-Host: hphalle5h.informatik.tu-muenchen.de
- Originator: fischerj@hphalle5h.informatik.tu-muenchen.de
-
-
-
- Well, I do not touch my bltnode struc until cleanup was called...
-
- My routines using Qblit (doing a pack of quite large blits) run
- well, until I start my picviewer, which fires off a blitbitmaprastport
- for each line in the window.
-
- Sooner or later, blitter will be locked :(
- Just locked, no wrong blits up to now detected.
- Leting the viewer draw in bigger steps doesn't change anything.
-
- I don't have an idea what you can do wrong on a blitbitmaprastport
- call. Well my bitmap got more width and different depth, is this illegal ?
-
- One thing is unclear about the bltnode: bltsize. what the hell to write
- in bltsize if I use large blits :\ well, both specifying 0 or a dummy value
- will work until my blitbitmaprastporter starts.
-
- The really funny thing is no other interference of both programs with
- windows, kingcon, whatever detectecd.
-
-
- Question to the RKM experts: I found a bug :)
-
- In blibitmaprastport, the interface is decsribed like
-
- Asm: D3
- C: WORD
-
-
- Another routine (blttemplate? don't remember) was described like this:
-
- Asm: D3.W
- C: WORD
-
- well, EXTing the values for my blitbitmap call didn't change anything...
-
- ------------------------------------------------------------------------
- fischerj@Informatik.TU-Muenchen.DE (Juergen "Rally" Fischer) =:)
-
-